System and method for providing carrier-independent VoIP communication

ABSTRACT

Systems and methods for seamlessly providing carrier-independent VoIP calls initiated using an existing carrier-issued telephone number are provided. In exemplary embodiments, the existing carrier-issued telephone number to be called is received. Subsequently, a status regarding if the existing carrier-issued telephone number is a registered telephone number stored in a carrier-independent database is determined. If the existing carrier-issued telephone number comprises a registered telephone number in the carrier-independent database, a call is established via peer-to-peer connection using an address associated with the registered telephone number. However, if the existing carrier-issued telephone number is not a registered telephone number in the carrier-independent database, the call is placed via a standard route.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is a Continuation of U.S. Nonprovisional patent application Ser. No. 16/154,437 filed 8 Oct. 2018; which is a Continuation of U.S. Nonprovisional patent application Ser. No. 12/228,301 filed 11 Aug. 2008, now U.S. Pat. No. 10,097,695 issued 9 Oct. 2018; which claims the benefit of U.S. Provisional Patent Application Ser. No. 60/964,295 filed 10 Aug. 2007; each of which is incorporated herein by reference in its entirety for all purposes.

BACKGROUND OF THE INVENTION

Embodiments of the present invention relate generally to communication systems and more particularly to providing carrier-independent VoIP communication.

Conventionally, peer-to-peer calling services exist (e.g., Skype and voice chat services). However, these services require a caller to select, prior to a call, to place the call over the peer-to-peer calling service. As such the caller must proactively instruct the system to place the call via a designated calling service.

A further disadvantage is that the caller must have knowledge that the call recipient also participates in the same calling service in order to use the calling service. Often times, the caller will not know whether this is the case. Additionally, if the call recipient is not using the same calling service, the peer-to-peer call service may not be available. If the caller decides to use a PSTN connection to place a call, or if their Internet connection is not of sufficient quality to place the call using peer-to-peer, the user must use a different device (e.g., standard telephone, other softphone software, etc) to place the call. Another disadvantage is that both parties must use phone numbers (or addresses) issued by their peer-to-peer carrier, and are not able to use standard phone numbers to reach each other over the free calling service.

SUMMARY OF THE INVENTION

Embodiments of the present invention comprise systems and methods for providing carrier-independent VoIP calls using existing carrier-issued phone numbers for both calling and receiving parties. This is a significant advancement over previous systems as it requires no change in user behavior. The user still picks up the same phone and dials the same telephone number, only now it uses VoIP and is a free call.

In exemplary embodiments, an existing carrier-issued telephone number to be called is received. Subsequently, a status regarding whether the existing carrier-issued telephone number is a registered telephone number in a carrier-independent database is determined. In exemplary embodiments, the existing carrier-issued telephone number may be used as a lookup key in the carrier-independent database. If the existing carrier-issued telephone number is registered, then a corresponding address for the registered telephone number may be determined from the carrier-independent database. The address may be dynamic or static. In exemplary embodiments, the address may comprise, for example, hostname, IP address, SIP address, MAC address, or any other addressing scheme which may be associated with a communication device.

If the existing carrier-issued telephone number comprises a registered telephone number in the carrier-independent database, a call may be established via a peer-to-peer connection using the address associated with the registered telephone number over a carrier-independent network. However, if the existing carrier-issued telephone number is not a registered telephone number in the carrier-independent database, the call is placed via a standard route. The standard route may comprise, for example, a third-party VoIP service which may not be free. In other embodiments, the standard route may comprise a communication over the PSTN 108.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an exemplary environment in which embodiments of the present invention may be practiced.

FIG. 2 is a diagram of an exemplary data center system according to one embodiment of the present invention.

FIG. 3 is a diagram of an exemplary call management system according to one embodiment of the present invention

FIG. 4 is a diagram illustrating an exemplary telephone number verification process.

FIG. 5 is a diagram illustrating an exemplary call connection process.

FIG. 6 is a diagram illustrating an exemplary call quality control process.

FIG. 7 is an example of a screenshot for establishing dial plans.

FIG. 8 is a flowchart of an exemplary method for providing carrier-independent VoIP communication.

DETAILED DESCRIPTION OF THE INVENTION

Embodiments of the present invention comprise systems and methods for providing seamless and automated selection of a carrier-independent VoIP communications call route between users using standard carrier-issued phone numbers, when available, and automated fallback to a standard route when not available. At a high level, the present invention provides a toll or network bypass technology for conducting communications over an Internet Protocol (IP) network. At a more specific level, the present invention provides a service that uses a familiar address space or communication identifier of “telephone numbers” to connect any two network or communication devices or “callers” via IP, thus bypassing natural toll charges that may occur to one or both parties if the call were to traverse traditional carrier network(s). Embodiments may be practiced with no interaction required by the caller or user. For simplicity, the carrier-independent communication service provided by exemplary embodiments of the present invention may be referred to herein as trixNet service.

In exemplary embodiments, the existing telephone numbers of any carrier is resolved to a hostname or address (e.g., IP address, SIP address, MAC address, or any other addressing scheme) so that users of a calling PBX may dial other users of a receiving PBX using standard carrier-issued telephone numbers (e.g., ANI numbers), yet actually connect to each other's PBX for free over IP. While exemplary embodiments are discussed in reference to telephone numbers, those skilled in the art will appreciate that other communication identifiers may be used. Advantageously, users do not need to switch carriers, as embodiments of the present invention are carrier-independent. As such, the telephone number can be issued and “owned” by any carrier or provider, but used by embodiments of the present invention. Users also do not need to know each other or even be aware that other users are participating in usage of the trixNet service as exemplary embodiments use the normal behavior patterns of dialing standard carrier-issued phone numbers. As a result, the telephone number of the caller and recipient may both be owned by different carriers, but the call remains 100% free.

FIG. 1 shows an exemplary environment 100 in which embodiments of the present invention may be practiced. The exemplary environment 100 comprises user areas 102 a and 102 b and a data center system 104 coupled via an IP network 106. In one embodiment, the user area 102 a may initiate a call to the user area 102 b. In other words, user area 102 a may comprise one registered user of the trixNet service and user area 102 b may comprise another registered user of the trixNet service. The IP network 106 may comprise the Internet or any other wide area network configured to provide communications via IP. In contrast, a public switch telephone network (PSTN) 108 allows calls to be made using POTS.

The data center system 104 is configured to provide enhanced calling service including providing carrier-independent VoIP service to users seamlessly. In exemplary embodiments, the user area 102 may communicate with the data center system 104 via a VPN connection. This allows for communication without the need to open any firewall ports at the user area 102. The data center system 104 will be discussed in more detail in connection with FIG. 2 below.

The user area 102 may comprise, for example, an office area, home area, or any other area comprising one or more network devices 110 coupled to the IP network 106 and PSTN 108 via a call management system 112. Each network device 110 may be associated with an individual user. The network devices 110 comprise communication devices which are configured to place a call (e.g., an IP phones, computer, or softphones) including analog devices (e.g., analog phones or fax machines). The network devices 110 are also configured to receive a call via a receiving PBX. Furthermore, calls may also be received by mobile phone devices (if those calls are being forwarded or “handed-off” to a mobile device or registered to a carrier or provider that practices embodiments of the present invention).

The call management system 112 is configured to route calls either through the IP network 106 or the PSTN 108. In exemplary embodiments, the call management system 112 functions as, or comprises, a PBX and a router. The PBX allows the network device 110 to make calls via the PSTN 108. In some embodiments, the PBX may be an iPBX server capable of serving VOIP communications. The router allows the network device 110 to make VoIP calls via the IP network 106 (in lieu of an iPBX). The call management system 112 will be discussed in more detail in connection with FIG. 3 .

In some embodiments, the IP network 106 may couple the user area 102 a to one or more remote user areas 114. The remote user area 114 may be a location associated with an individual that remotely accesses the user area 102 a. For example, the remote user area 114 may be a home office of an employee associated with the user area 102 a. The remote user area 114 may also comprise one or more network devices 110 (e.g., a computer). Any number of remote user areas 114 may be coupled to the user area 102 a. Additionally, it should be noted that “remote” as used herein refers to any environment external to an enterprise central location (i.e., user area 102 a).

According to exemplary embodiments, the users within any of the areas (e.g., user areas 102 and remote user area 114) may exchange calls. Ideally, the users want the phone call to be directed through a free VoIP service when available in order to save on phone charges. This VoIP call may be placed using the IP network 106. Alternatively, when VoIP is not available, the call may be placed via the PSTN 108. It should be noted that calls may also be accepted by an auto-attendant (e.g., interactive voice recognition—IVR) of the receiving PBX, or even initiated by an auto-attendant of the calling PBX and bypass the need for a user (i.e., human) on either or both ends of the call.

In exemplary embodiments, trixNet service is network ubiquitous. That is, neither the calling nor receiving party needs to be geographically close to either the calling or receiving PBX. Users of either PBX can be telecommuters, fixed home workers, or mobile users so long as both parties are registered devices/users with their respective PBXs. The sending and receiving network devices 110 may simply be participating in the trixNet service. It should be noted that in some embodiments, the term PBX may be used interchangeably with the call management system 112.

The trixNet service may take many forms. In one embodiment, trixNet service may be implemented as a remote network service, which elegantly folds into a hybrid-hosted architecture. trixNet may also be implemented in a peer-to-peer fashion whereby a “directory” (e.g., relational database of IP addresses) is stored on each node or on super nodes (e.g., on the call management system 112) such that resolving of phone numbers to network locations is decentralized. An exemplary discussion of a hybrid-hosted architecture can be found in U.S. patent application Ser. No. 11/506,279 entitled “Mobile Use of a PBX System,” which is incorporated by reference. It should be noted that trixNet service does not necessarily have to be implemented on a PBX. trixNet may be used, in one embodiment, at a consumer level to connect any two network devices 110 (e.g., a computer) for a one-to-one calling relationship instead of between two PBXs for a many users-to-many-users calling relationship.

Referring now to FIG. 2 , the data center system 104 is shown in more detail. The data center system 104 is configured to provide enhanced calling service including providing carrier-independent VoIP communications to users seamlessly. In exemplary embodiments, the data center system 104 comprises a management interface module 202, registration module 204, relational database 206, verification module 208, routing instruction module 210, system monitoring module 212, and update module 214. It should be noted that the data center system 104 may comprise one or more servers.

The exemplary management interface module 202 is configured to provide a user interface for management of the trixNet service. When a trixNet user opts to enroll a telephone number into the trixNet service, the user may enter a telephone number in this user interface. By providing the user interface over the IP network 106 (e.g., Internet), an administrator or user may manage any telephone number from any location in the world.

The registration module 204 is configured to receive and process registration information for the trixNet service. In exemplary embodiments, the registration information may comprise at least an existing, standard carrier-issued phone number and an address (e.g., IP address, hostname, SIP address, MAC address, etc.) associated with the telephone number. The telephone number and the address may be stored in a relational database 206, which maps the telephone number and the address.

In one embodiment, trixNet service comprises a verification process performed by the verification module 208. This verification process prevents people from stealing other people's telephone numbers and unethically diverting all “in-network” trixNet phone traffic to their PBX. In this embodiment, the verification module 208 will trigger a call to the carrier-issued telephone number being registered to verify ownership. The user may then be asked to press a certain key or series of keys (i.e., DTFM sequence) to verify that they want to add the carrier-issued telephone number into the trixNet service. Once a user has validated a telephone number by pressing the correct key(s), the carrier-issued telephone number is considered authorized and a formal part of the trixNet service to be reached, for free, by any other trixNet user dialing that carrier-issued telephone number. It should be noted that a carrier-issued telephone number may be re-verified at any time, which may gracefully handle carriers who use local number portability (LNP) to move telephone numbers to different users or carriers.

The routing instruction module 210 is configured to determine a correct address associated with the carrier-issued telephone number. In exemplary embodiments, the routing instruction module 210 will receive the carrier-issued telephone number entered by the user via their network device 110 and sent via the call management system 112. The routing instruction module 210 then accesses the relational database 206 and uses the carrier-issued telephone number as a lookup key to determine if a corresponding address is mapped to the telephone number. The address may then be sent back to the call management system 112 in order to initiate the call via VoIP.

The system monitoring module 212 is configured to test a peer-to-peer connection between two addresses. In some embodiments, when a request for a peer-to-peer connection is made, the system monitoring module 212 may check the connection to ensure quality and/or availability of the connection. The results of the test may be provided to the call management system 112. It should be noted that in some embodiments, the call management system 112 may perform the testing of the peer-to-peer connection, as will be discussed further below.

The exemplary update module 214 is configured to provide updates to the call management system 112. In one embodiment, the update module 214 may provide software updates. In a decentralized embodiment, the update module 214 may provide updated relational database information to the nodes storing local versions of the relational database 206. These nodes may comprise other modules of the data center system 204. In one embodiment, the call management system 112 may comprise a node that maintains a local copy of the relational database, as will be discussed further below.

Referring now to FIG. 3 , the exemplary call management system 112 is shown in more detail. In exemplary embodiments, the call management system 112 comprises a PBX 302 and router 304. The PBX 302 is configured to provide communications via the PSTN 108, while the router 304 is configured to provide communications (e.g., VoIP) via the IP network 106. In some embodiments, the PBX may comprise an iPBX, which eliminates the need for the router 304. The call management system 112 may further include one or more memory devices 306. The memory device 306 comprises a communication interface module 308, dynamic address engine 310, settings module 312, call routing module 314, fallback module 316, and local relational database 318.

The communication interface module 308 is configured to provide a user interface for configuring and managing functions of the call management system 112. For example, an administrator is able to create VoIP accounts and establish dial plans via the interface provided by the communication interface 306 of the call management system 112.

In exemplary embodiments, the dynamic address engine 310 is configured to handle private addresses. The dynamic address engine 310 may operate to determine and maintain a list of private (internal) addresses associated with each network device 110 coupled to the call management system 112. The dynamic address engine 310 may comprise, at least, an address check module and local lookup module as discussed in U.S. patent application Ser. No. 11/506,279 entitled “Mobile Use of a PBX System,” which is incorporated by reference.

As such, embodiments of the present invention allow either the calling call management system 112 or the receiving call management system 112 (PBX or router) to use dynamic (constantly-changing) addresses. This is a by-product of the hybrid-hosted architecture which continually tracks the address of both the calling and receiving PBX. Addresses may change dynamically during a call and embodiments of the present invention will be able to keep the call active and prevent it from terminating. An example of the hybrid-hosted architecture may be found in U.S. patent application Ser. No. 11/827,314, filed Jul. 11, 2007 and entitled “System and Method for Centralized Presence Management of Local and Remote Users,” which is incorporated by reference.

The settings module 312 is configured to receive (via the interface provided by the communication interface 308) and maintain settings for the call management system 112. For example, VoIP accounts may be established and maintained via the settings module 312. Furthermore, dial plans for various calling options may be managed using the settings module 312.

The exemplary call routing module 314 is configured to route the requested call through the proper network (i.e., IP network 106 or PSTN 108) to a proper telephone number or address. In some embodiments, the call routing module 314 may send a telephone number to the data center system 104 in order to determine if an address linked to that phone number is available for routing purposes. The call routing module 314 may then receive a response from the routing instruction module 210 of the data center system 104 comprising an associated address (e.g., hostname, IP address, SIP Address, MAC address, etc.), if available. The call routing module 314 may then instruct the PBX 302 or the router 304 to initiate the communication using the telephone number (for PSTN calls) or the address (for VoIP calls).

The exemplary fallback module 316 is configured to monitor call quality and handle an auto-fallback process. The auto-fallback process may occur when the call management system 112 cannot reach a receiving call management system 112 (PBX or router) via the IP network 106. Furthermore, auto-fallback may occur when for example, the fallback module 316 determines that quality of the free trixNet call is, or will be, poor (e.g., by using any qualitative means of measurement such as round-trip ping time, jitter, sine-wave audio echo analysis, live MOS scoring). As such, the free trixNet call is able to automatically “fall back” to a normal trunking that the calling call management system 112 uses (e.g., VoIP, analog, or TDM). This “fall-back” occurs in milliseconds or seconds and may be transparent to the user. Advantageously, the user does not have to specify that they want to make a free call. The call management system 112 tries for the free call, then goes paid if it cannot or determines it does not want to (e.g., quality is poor) go free.

The optional local relational database 318 stores telephone numbers of trixNet members in a relational database. In some embodiments, these telephone numbers may be mapped to a dynamic address associated with the dynamic address engine 310. If dynamic addresses are used (e.g., those used by cable modem or DSL services), the address associated with that telephone number is automatically updated. In other embodiments, the local relationship database 318 may comprise a copy of the relational database of the data center system 104, thus enabling peer-to-peer communications without access to the data center system 104.

FIG. 4 is a diagram illustrating an exemplary telephone number verification process. When a trixNet user (e.g., subscriber to trixNet services) opts to enroll an existing carrier-issued telephone number, the user may enter the telephone number in a web interface provide by the management interface module 202. In order to avoid abuse, the verification module 208 will initiate the verification process. Initially, a membership request is sent from the call management system 112 to the data center system 104. The membership request may comprise, at least, a telephone number which the user wants to register for trixNet service.

Upon receipt of the membership request, the verification module 208 initiates a PSTN call to the entered carrier-issued telephone number being registered. The PSTN call may request a user at the telephone number to provide a response to the verification module 208. In one embodiment, the response may be a DTMF entry of a validation code given via verbal instructions. Only if the code is entered correctly is the number entered into the relational database and registered for trixNet service. Should the number be re-assigned via the PSTN to another user, the number may be revalidated at any time by request of the owner of the telephone number in accordance with one embodiment.

In some embodiments, trixNet service may be used on an “opt-in” (e.g., users must register phone numbers) or opt-out basis. As such, trixNet may be used in a partial manner on a PBX, whereby some phone numbers (e.g., DIDs) participate in trixNet services and some phone numbers do not.

Referring now to FIG. 5 , a diagram illustrating an exemplary call connection process is shown. When a carrier-issued telephone number is dialed at the network device 110, a request may be made via a data connection to the relational database 206 using the dialed carrier-issued telephone number as a lookup key. A status of the dialed carrier-issued telephone number is then returned by the routing instruction module 210. If the carrier-issued telephone number is not in the relational database 206, the call is routed via the standard third-party routes chosen by the user (or their administrator). The standard third-party route may comprise, for example, a third-party VoIP service, which may not be free. In other embodiments, the standard third-party route may comprise a communication over the PSTN 108. If the carrier-issued telephone number is in the relational database 206, a peer-to-peer VoIP connection may be initiated, connecting the call via the network 106 using the mapped address, which circumvents the PSTN 108 completely.

Referring now to FIG. 6 , a diagram illustrating an exemplary call quality control process is shown. When a call is placed from one trixNet user to another, the availability and quality of the connection may be tested or monitored in real-time. Connection quality can be determined by a user-specific set of specifications, including but not limited to jitter, latency, sine-wave audio echo analysis, and live MOS scoring. If quality is determined to be within specification, the call is placed via the peer-to-peer trixNet connection. If the quality is not within specification, the call may automatically fall back to the standard connection chosen by the user (e.g., third-party VoIP or PSTN). In exemplary embodiments, the monitoring and fallback may be performed by the fallback module 316. In some embodiments, the monitoring may be performed, in part, by the system monitor module 212.

In one embodiment, the PBX 302 or call management system 112 administrators may build dial-plans that specifically include or exclude trixNet services. This allows a non-holistic implementation of trixNet services whereby a user can indicate on a per call basis if they want to participate in trixNet service. FIG. 7 illustrates an exemplary user interface 700 provided by the communication interface module 308 for establishing dial plans. Via the dial plan user interface 700, dial strings, descriptions, type, and primary routes may be provided. For example, a dial plan may be established whereby the user first dials 8 to make a trixNet call or first dials 9 to make a normal call. Another example may comprise providing the users with a software application, such as HUD, whereby the users may indicate automatic or partial inclusion into the trixNet service on a per call or holistic basis. An exemplary discussion of the HUD application is found in U.S. patent application Ser. No. 11/827,314, filed Jul. 11, 2007 and entitled “System and Method for Centralized Presence Management of Local and Remote Users,” which is incorporated by reference.

FIG. 8 is a flowchart 800 of an exemplary method for seamlessly providing carrier-independent VoIP communication using existing standard carrier-issued telephone numbers. In step 802, dialing instructions are received from a registered trixNet user (e.g., via a registered trixNet network device having a registered telephone number). In exemplary embodiments, the dialing instructions comprise a carrier-issued telephone number associated with a call recipient. A request to check the relational database 206 is sent in step 804 to determine if the carrier-issued telephone number is a registered telephone number for trixNet service.

Using the carrier-issued telephone number as a lookup key, a determination is made as to whether the carrier-issued telephone number is registered in the carrier-independent relational database 206 in step 806. If the carrier-issued telephone number is not in the relational database 206, then the call is routed via the standard third-party route chosen by the user (or their administrator) in step 808. The standard third-party route may comprise, for example, a third-party VoIP service, which may not be free. In other embodiments, the standard third-party route may comprise a communication over the PSTN 108.

If the carrier-issued telephone number is in the relational database, this indicates that the carrier-issued telephone number is registered for trixNet service. Since both the caller and call recipient are using trixNet registered network devices (e.g., via their registered carrier-issued telephone numbers), the call may be established for free over a (trixNet) carrier-independent network. As such, a peer-to-peer connection may be requested in step 810. In exemplary embodiments, the mapped address is determined. The address may then be returned to the call management system 112, which requests establishment of the peer-to-peer connection.

The peer-to-peer connection between the two addresses (of the caller and call recipient) may be tested in step 812 in order to ensure availability and quality. In one embodiment, the system monitoring module 212 of the data center system 104 may check the quality and availability of the IP network 106. In other embodiments, the fallback module 316 of the call management system 112 may check the quality or availability of the IP network 106.

If in step 814, the peer-to-peer connection exceeds the acceptable specification established by user (or their administrator), then the VoIP call may be established in step 816. However, if the acceptable specifications are not exceeded, then the call is routed via the standard third-party route chosen by the user (or their administrator) in step 808.

It should be noted that FIG. 8 is exemplary. More, less, or functionally equivalent steps may be embodied in alternative embodiments. Furthermore, the steps may be practiced in a different order. For example, the carrier-independent VoIP call may be initially established. Subsequently, the peer-to-peer connection may be tested (e.g., in real-time) for quality and other requirements established in the user-specified standard to determine if the call should fall back to the standard third-party route.

It should be noted that trixNet can federate with other calling services such as Skype or GoogleTalk and even other calling directories such as eNUM, FWD, or other number resolving schemas. Additionally, trixNet can be extended with APIs so that other calling services or directories can federate with trixNet users.

The above-described functions and components can be comprised of instructions that are stored on a storage medium. The instructions can be retrieved and executed by a processor. Some examples of instructions are software, program code, and firmware. Some examples of storage medium are memory devices, tape, disks, integrated circuits, and servers. The instructions are operational when executed by the processor to direct the processor to operate in accord with embodiments of the present invention. Those skilled in the art are familiar with instructions, processor(s), and storage medium.

The present invention has been described above with reference to exemplary embodiments. It will be apparent to those skilled in the art that various modifications may be made and other embodiments can be used without departing from the broader scope of the invention. For example, each node may comprise some or all of the functions and modules associated with the call data system 204 in decentralized embodiments. The node may be the call management system 112 in one embodiment. Therefore, these and other variations upon the exemplary embodiments are intended to be covered by the present invention. 

The invention claimed:
 1. A method comprising: serving, by a server, a graphical user interface (GUI) to a first client operated by a first user, wherein the GUI includes depicts a form having a set of user input elements configured for receiving a set of user inputs by the first user; receiving, by the server, the set of user inputs from the first client; formulating, by the server, a set of parameters for a communication, wherein the set of parameters is based on the set of user inputs; and causing, by the server, the communication to occur based on the set of parameters, wherein the communication is between the first client operated by the first user and a second client operated by a second user, wherein the communication occurs based on: receiving, by the server, a first telephone number from the first client as input by the first user, wherein the first telephone number is a carrier issued telephone number; searching, by the server, a database for a second telephone number matching the first telephone number in value, wherein the second telephone number is a registered telephone number; locating, by the server, the second telephone number in the database; identifying, by the server, an electronic address corresponding to the second telephone number in the database; and causing, by the server, the communication to be placed from the first client to the second client based on the electronic address via a carrier independent peer-to-peer connection between the first client and the second client via the server.
 2. The method of claim 1, wherein the communication occurs further based on: causing, by the server, the communication to be placed from the first client to the second client not via the carrier independent peer-to-peer connection based on not locating, by the server, the second number in the database.
 3. The method of claim 1, wherein the set of parameters includes at least one of a dial string, a description, a type, or a primary route.
 4. The method of claim 1, wherein the set of parameters includes a preset number that the first user first dials to make the communication over the carrier independent peer-to-peer connection.
 5. The method of claim 1, wherein the communication occurs further based on: testing, by the server, the carrier independent peer-to-peer connection such that a determination whether a user specification is acceptable occurs.
 6. The method of claim 5, further comprising: causing, by the server, the communication to be placed from the first client to the second client not via the carrier independent peer-to-peer connection based on the user specification being not acceptable.
 7. The method of claim 1, wherein the carrier independent peer-to-peer connection is a 3{circumflex over ( )} party VoIP connection.
 8. The method of claim 1, wherein the first telephone number is a lookup key in the database.
 9. The method of claim 1, wherein the server is a iPBX server.
 10. The method of claim 1, wherein the database is a first database, wherein the first database is updateable off a second database remote to the server such that the first database contains a copy of the second database.
 11. A system comprising: a server programmed to: serve a graphical user interface (GUI) to a first client operated by a first user, wherein the GUI includes depicts a form having a set of user input elements configured for receiving a set of user inputs by the first user; receive the set of user inputs from the first client; formulate a set of parameters for a communication, wherein the set of parameters is based on the set of user inputs; and cause the communication to occur based on the set of parameters, wherein the communication is between the first client operated by the first user and a second client operated by a second user, wherein the communication occurs based on: receive a first telephone number from the first client as input by the first user, wherein the first telephone number is a carrier issued telephone number; search a database for a second telephone number matching the first telephone number in value, wherein the second telephone number is a registered telephone number; locate the second telephone number in the database; identify an electronic address corresponding to the second telephone number in the database; and cause the communication to be placed from the first client to the second client based on the electronic address via a carrier independent peer-to-peer connection between the first client and the second client via the server.
 12. The system of claim 11, wherein the server is programmed for the communication to occur further based on: cause the communication to be placed from the first client to the second client not via the carrier independent peer-to-peer connection based on not locating the second number in the database.
 13. The system of claim 11, wherein the set of parameters includes at least one of a dial string, a description, a type, or a primary route.
 14. The system of claim 11, wherein the set of parameters includes a preset number that the first user first dials to make the communication over the carrier independent peer-to-peer connection.
 15. The system of claim 11, wherein the server is programmed for the communication to occur further based on: test the carrier independent peer-to-peer connection such that a determination whether a user specification is acceptable occurs.
 16. The system of claim 15, wherein the server is further programmed to: cause the communication to be placed from the first client to the second client not via the carrier independent peer-to-peer connection based on the user specification being not acceptable.
 17. The system of claim 11, wherein the carrier independent peer-to-peer connection is a 3{circumflex over ( )} party VoIP connection.
 18. The system of claim 11, wherein the first telephone number is a lookup key in the database.
 19. The system of claim 11, wherein the server is a iPBX server.
 20. The system of claim 11, wherein the database is a first database, wherein the first database is updateable off a second database remote to the server such that the first database contains a copy of the second database. 